Document registry SHA-pin recovery after in-place republish#8
Merged
Conversation
Registry versions are immutable; rebuilt assets need a suffixed registry version (e.g. 0.10.500.1) plus status-delete of the stale entry. Learned the hard way on the cwd-fix republish. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Registry versions are immutable; an in-place asset republish invalidates the pinned SHAs. Documents the recovery used for 0.10.500 -> 0.10.500.1 (suffixed registry version + status-delete of the stale entry).
?? Generated with Claude Code